DAOS-18785 object: handle resent RPC on DTX non-leader - b28#17989
Merged
gnailzenh merged 1 commit intorelease/2.8from Apr 17, 2026
Merged
DAOS-18785 object: handle resent RPC on DTX non-leader - b28#17989gnailzenh merged 1 commit intorelease/2.8from
gnailzenh merged 1 commit intorelease/2.8from
Conversation
|
Ticket title is 'test_ec_multiple_rank_failure failed during IOR: dfs_write(0x558292ef2000, 2048) failed (5): Input/output error' |
Nasf-Fan
force-pushed
the
Nasf-Fan/DAOS-18785_b28
branch
3 times, most recently
from
5ace005 to
1b23afb
Compare
Usually, most of resent RPCs will be detected and handled on DTX leader. But when DTX leader is switched, such as old DTX leader is dead/evicted, the DTX for some inflight IO maybe in 'prepared' status on a non-leader while related client resends the RPC to new DTX leader. Under such case, DTX-resync may has not handled such DTX in time. Then IO handler on the non-leader needs to check whether related DTX has ever been prepared or not: if yes, directly reply to the DTX leader to avoid misguiding lower layer logic as to generate confused error. Add new test case for that. Allow-unstable-test: true Signed-off-by: Fan Yong <[email protected]>
Nasf-Fan
force-pushed
the
Nasf-Fan/DAOS-18785_b28
branch
from
1b23afb to
1d3a130
Compare
Collaborator
|
Test stage Functional Hardware Medium MD on SSD completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17989/6/testReport/ |
Contributor
Author
test_dfuse_daos_build_wb failed for DAOS-18813, not related with the patch. |
Nasf-Fan
added
the
clean-cherry-pick
wangshilong
approved these changes
Apr 17, 2026
liuxuezhao
approved these changes
Apr 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Usually, most of resent RPCs will be detected and handled on DTX leader. But when DTX leader is switched, such as old DTX leader is dead/evicted, the DTX for some inflight IO maybe in 'prepared' status on a non-leader while related client resends the RPC to new DTX leader. Under such case, DTX-resync may has not handled such DTX in time. Then IO handler on the non-leader needs to check whether related DTX has ever been prepared or not: if yes, directly reply to the DTX leader to avoid misguiding lower layer logic as to generate confused error.
Add new test case for that.
Allow-unstable-test: true
Steps for the author:
After all prior steps are complete: